(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Top Support Issues
DOCUMENT ID#: FYI.P.6119
DATE: 08Jan93
PRODUCT: NetWare Lite
PRODUCT VERSION: All versions
SUPERSEDES: FYI.P.6085
SYMPTOM: NA
ISSUE/PROBLEM
Top Support Issues
SHARE.EXE: Status Report 5
When loading SERVER.EXE, you may get "Status Report 5," which means that SHARE.EXE has not been loaded. SHARE.EXE is a program that comes with DOS 3.1 or above. SHARE is the mechanism that allows files to be accessed simultaneously from multiple clients. If you get Status Report 5, you either do not have SHARE.EXE in your PATH, or you do not load it anywhere before SERVER.EXE is loaded. Either add the appropriate directory to your PATH (where SHARE.EXE is located) or copy SHARE.EXE to the directory where NetWare Lite is installed. Although loading SHARE is not required for the server to run, it is strongly recommended. SHARE should be loaded before SERVER. SHARE should be tuned for proper performance. You may need to increase the values for locks (/L) and files (/F) if you run database applications or if you have more than 4 users accessing the server. See your DOS documentation for more information on configuring SHARE. You do not need to load SHARE before loading CLIENT. See SHARE fax documentation for more information.
Setting LASTDRIVE
LASTDRIVE is a DOS command which is executed at boot time from the CONFIG.SYS file. The NetWare Lite NET utility uses LASTDRIVE to identify valid drives and to provide compatibility with other NetWare products. The installation programs default value of LASTDRIVE=M: should work for most situations. If you wish to use a value other than M: be aware that LASTDRIVE should be set to G: or greater for NET to run. LASTDRIVE is set by including a command such as "LASTDRIVE=G:" in CONFIG.SYS. If you attempt to run NET with LASTDRIVE set lower than G:, or not set, you will have to increase the value of LASTDRIVE and reboot before any NET command can be executed.
The IPXODI Driver
The IPX shipped with NetWare Lite (IPXODI) is not new and is not special to NetWare Lite. Novell has made a general decision to convert from "linked" IPX to IPXODI. IPXODI is shipped with the LAN Workplace for DOS product, and with DOS/Windows shell kit. IPXODI is functionally identical to the linked version of IPX, although the LSL offers multiple-protocol and MLID capabilities. NetWare Lite can be run on top of either (but not both) linked IPX or IPXODI. STARTNET.BAT, which is created as part of the NetWare Lite installation, should be modified to NOT load LSL (the odi driver) and IPXODI if linked IPX is already being loaded elsewhere (like in your AUTOEXEC.BAT). See fax document #118 for more information.
Windows
Some NetWare Lite users have had trouble getting Windows 3.0 to run smoothly with NetWare Lite. This document (#210) gives some hints as to how to configure both NetWare Lite and Windows 3.0 in order to gain better performance. All Windows/NetWare Lite users should download this document.
For Windows v3.1 download documents #204 and more importantly get #206.
Network Applications
Installing applications on NetWare Lite may be different than installing applications on NetWare. NetWare is, as you know, a very popular LAN. Many applications have NetWare specific installation options. These installation options DO NOT apply to NetWare Lite networks. NetWare Lite is a DOS peer-to-peer network. If the application being installed has network specific installations then "Other networks.." or "DOS peer-to-peer network" or the like, should be selected. DO NOT select NetWare or Novell installation options. See Appendix B in the documentation for more details about using NetWare Lite with NetWare. Please see fax document #211 for more information.
Connections
Many of the problems that NetWare Lite technical support deals with are related to network connections. Connection problems become the culprits who cause many other seemingly unsolvable problems. Most of these connections problems are caused by bad or mis-configured hardware, drivers, memory managers, etc. This document (#215) explains how to troubleshoot and overcome "connection" problems.
Installing "other" Network Interface Card Drivers
When loading NetWare Lite you are prompted to select a network interface card driver. Unfortunately, the installation program fails to complete properly if "other" is selected. If you need to use a card driver not supplied on the original installation diskettes, you can avoid this problem by making a backup copy of the original diskettes and copying the card driver to this backup. Use the new diskette to install NetWare Lite. Note: If you make a separate backup of the "driver" diskette you must copy your card driver to the "driver" backup. See fax document "Selecting Other Card Driver During Installation" (#217) for a step-by-step procedure on how to do this.
Network Setup
This document (#235) gives the user tips on how to configure the network. It explains mappings, captures, and network resources. It also goes through an example of a network configuration.
Patches
Novell has released several patches that should be applied by NetWare Lite users who have problems that they are unable to solve. Please see document #263 for more information on how to get the v1.0 patches and #265 for v1.1 patches.
Updates
Some files are in need of upgrading in NetWate Lite v1.1. Download document #267 for details on acquiring and installing the upgrades.
Resolving I/O and IRQ Conflicts
Document #212 gives a list of possible conflicts in hardware setup. Network Interface Cards (NICs) and other devices may have conflicting I/O addresses or interrupts. This list may clarify some of the problems.
NWLite 1.1 / Windows 3.1 Compatibility
This is a lengthy document similar to #205. It does contain more concise information concerning Windows 3.1 and particularly using it with NWLite v1.1. It will take you through different install methods and options depending on DOS versions being used. For indepth details see document #206.
Trouble Shooting Lockup (Hanging) Problems
Installing a Network system may be challenging particularly if a lockup is encountered. Several things may cause this and document #218 gives ideas to help diagnose such problems. It explains hardware or switch setting conflicts, memory conflicts, bad hardware, software conflicts or the need of configuration changes.
DOS Memory Managers and NetWare Lite v1.x
This is an overview to help create the best performing servers and clients and how to utilize memory. Inclusive is how to load NWLite files into upper memory. The use of memory managers and different DOS commands for such. See #264 for detail and for NetWare Lilte v1.1 download #266.
Printing
Printing with NetWare Lite is fairly simple but their are some questions which may come up. If you have problems or questions download document #240 and for possible solutions to printing download #227.
